True push architecture for internet protocol notification

ABSTRACT

A method of true push for internet protocol notification to a mobile communication device implemented by at least one server computer. The method comprises determining the size of physically addressable random access memory (RAM) and the number of central processing unit (CPU) cores of the server computer at boot time and setting the resource limit, rlimit, in the kernel of the server computer that comprises setting the limit for the total number of file handles in the entire system automatically based on the determined size of the random access memory and the determined number of the central processing unit cores at boot time. The method further comprises tying the memory page allocation into the setting of the kernel parameters, whereby the input/output (I/O) maintenance of the server computer is maximized for concurrent web sockets so that the server computer is optimized for implementing the true push for internet protocol notification.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of and claims priority under 35U.S.C. §120 to U.S. patent application Ser. No. 13/949,228, filed onJul. 24, 2013, entitled “True Push Architecture for Internet ProtocolNotification”, by Lyle T. Bertz, et al., which is incorporated herein byreference in its entirety for all purposes.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

Not applicable.

REFERENCE TO A MICROFICHE APPENDIX

Not applicable.

BACKGROUND

Data network capable electronic devices are becoming increasinglyprevalent in our daily lives. Additionally, more and more electronicdevices that did not have data network capabilities are being providedwith data network capabilities. With the rapid development andpopularization of data network capable electronic devices, a widevariety of increasingly sophisticated techniques are being deployed byelectronic device manufacturers and wireless communications serviceproviders to help in marketing and promoting applications and brands todata network capable electronic devices. The development of onlineapplication stores also helps distribute applications and advertisementsacross the network. However, too many or too frequent advertisements andtheir impact on the user experience may have implications for usersatisfaction with the electronic device manufacturer and/or the wirelesscommunications service provider.

SUMMARY

In an embodiment, a method of true push for internet protocolnotification to a mobile communication device implemented by at leastone server computer is disclosed. The method comprises determining thesize of physically addressable random access memory (RAM) and the numberof central processing unit (CPU) cores of the server computer at boottime and setting the resource limit, rlimit, in the kernel of the servercomputer that comprises setting the limit for the total number of filehandles in the entire system automatically based on the determined sizeof the random access memory and the determined number of the centralprocessing unit cores at boot time. The method further comprises tyingthe memory page allocation into the setting of the kernel parameters andsetting the central processing unit core affinity to a single thread forthe server computer by an application on the server computer to avoidcontext switching between applications, whereby the input/output (I/O)maintenance of the server computer is maximized for concurrent websockets so that the server computer is optimized for implementing thetrue push for internet protocol notification.

In an embodiment, a method of true push for internet protocolnotification to a mobile phone implemented by at least one servercomputer is disclosed. The method comprises determining the size ofphysically addressable random access memory and the number of centralprocessing unit cores of the server computer at boot time to changekernel parameter settings, tying the memory page allocation into thesetting of the kernel parameter for the server computer and setting thenumber of file handles automatically for the server computer based onthe determined size of the random access memory and the determinednumber of central processing unit cores at boot time, whereby theinput/output maintenance of the server computer is maximized forconcurrent web sockets so that the server computer is optimized forimplementing the true push for internet protocol notification.

In an embodiment, a method of true push for internet protocolnotification implemented by at least one server computer is disclosed.The method comprises determining the size of physically addressablerandom access memory and the number of central processing unit cores ofthe server computer at boot time and changing parameters on the kernelof the server computer based on the size of the physically addressablerandom access memory and the number of central processing unit cores atboot time, whereby the input/output maintenance of the server computeris maximized so that the server computer is optimized for implementingtrue push for internet protocol notification.

These and other features will be more clearly understood from thefollowing detailed description taken in conjunction with theaccompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure, referenceis now made to the following brief description, taken in connection withthe accompanying drawings and detailed description, wherein likereference numerals represent like parts.

FIG. 1 is an illustration of a communication system according to anembodiment of the disclosure.

FIG. 2 is an illustration of a message flow of a communication systemaccording to an embodiment of the disclosure.

FIG. 3 is a flow chart illustrating a method according to an embodimentof the disclosure.

FIG. 4 is an illustration of a mobile communication device according toan embodiment of the disclosure.

FIG. 5 is a block diagram of a mobile communication device according toan embodiment of the disclosure.

FIG. 6A is a block diagram of a software architecture of a mobilecommunication device according to an embodiment of the disclosure.

FIG. 6B is a block diagram of another software architecture of a mobilecommunication device according to an embodiment of the disclosure.

FIG. 7 is a block diagram of a computer system according to anembodiment of the disclosure.

DETAILED DESCRIPTION

It should be understood at the outset that although illustrativeimplementations of one or more embodiments are illustrated below, thedisclosed systems and methods may be implemented using any number oftechniques, whether currently known or not yet in existence. Thedisclosure should in no way be limited to the illustrativeimplementations, drawings, and techniques illustrated below, but may bemodified within the scope of the appended claims along with their fullscope of equivalents.

Problems may occur when wireless communications service providers try tosend real time internet protocol notifications to mobile communicationdevices without true push architecture—for example the internet protocolnotification may not be delivered on time. Real time internet protocolnotifications may be sent within about 5 minutes of an event, about 1minute of an event, about 20 seconds of an event, or within another timeperiod of an event. With push technology, the request for acommunication transaction between a server and a client is initiated bythe information publisher or the server. On the other hand, with pulltechnology, the request for the transmission of information is initiatedby the information receiver or the client.

The standard approach to configuring the operating system kernel of ageneral purpose server computer may be to set a limit on the number offile handles available for establishing network connections to about 2²⁰(e.g., 1,048,576) or a like number. It is an insight of the presentdisclosure that for the specific purpose of supporting true push ofinternet protocol notifications, the performance of servers can beimproved by eliminating this limit and instead configuring the operatingsystem kernel of the server with a file handle limit determined by analgorithm taking into account the CPU configuration of the server, thememory of the server, and other hardware resources of the server. Thisalgorithmic determination of file handle limit may make many more filehandles available for use while avoiding the challenges of notconfiguring any limit on file handles. Likewise, the operating systemkernel of general purpose computers are typically configured to supportmulti-processing using what is commonly referred to as concurrentprocesses and context switching between processes, possibly numerousprocesses. It is another insight of the present disclosure that for thespecific purpose of supporting push of internet protocol notifications,as described more fully hereinafter, the operating system kernel of theserver may be configured to execute only a single process/thread—theprocess that pushes internet protocol notifications. One skilled in theart will appreciate how unusual is this restriction of a powerful serverto executing only a single process. These unusual configurations ofoperating system kernel parameters may provide efficiencies that allowfewer servers to perform true push for internet protocol notificationsthan would otherwise be needed if the servers were configured in thestandard way and as recommended by most server vendors for standardserver operations.

The problems may occur because the internet protocol notification may berealized by pull technology and because the internet protocolnotifications are staggered and delivered once or a few times over aperiod of time instead of whenever it is desired. The difficulties ofrealizing true push architecture for internet protocol notification maylie in keeping a large number of live concurrent network connectionsbetween the server and the mobile communication devices. For example,when a conventionally configured kernel of a server is utilized as is,the server may not be optimized for input/output purposes as may bedesirable for the true push functionality. The present disclosureteaches a method for adjusting the operating system kernel parameters tooptimize server computers for input/output performance and implementingtrue push architecture for internet protocol notifications on servercomputers.

For example, the physically addressable size of random access memory andthe number of central processing unit cores may be determined for kernelparameter settings in an automated manner, for example by a computerapplication. The operational or system overhead may also be includedinto consideration by the computer application for determining thekernel parameter settings. The resource limit parameters in the kernel,for example the limit for the total number of file handles in the entiresystem, may be set by the computer application based on the physicallyaddressable size of the random access memory, the number of centralprocessing unit cores, the system overhead, and/or another hardware orsoftware factor. The limit for the number of open input files in theentire system, the limit for the number of open output files in theentire system, and the limit for the number of concurrent networkconnections may be set by the computer application based on thephysically addressable size of random access memory and the number ofcentral processing unit cores.

In addition, the kernel parameters that define the limit for the numberof open files by a single process, the maximum size of a shared memorysegment, the minimum size of a shared memory segment, and the totalamount of shared memory available in the entire system of the server maybe determined and set by the computer application. The maximum number ofshared memory segments per process, the maximum number of shared memorysegments, or another resource limit may be set by the computerapplication. In an embodiment, the kernel parameters are automaticallyset to values by the computer application so that the random accessmemory may be utilized instead of disk memory. The memory pageallocation may be tied to the settings of the kernel parameters by thecomputer application. The central processing unit core affinity may beset to a single thread and/or to a single process by the computerapplication to avoid context switching between applications. In anembodiment, thread and process are equivalent for the true push internetprotocol notification system. This way, the server computer may beoptimized for input/output performance to maintain a large number oflive concurrent network connections that may realize true push forinternet protocol notifications.

Turning now to FIG. 1, a communication system 100 is described. In anembodiment, the system 100 comprises a plurality of mobile communicationdevices 102. The device 102 may comprise a processer 104, one or moreclient applications 106, a global positioning system (GPS) receiver 108,a radio transceiver 110, a memory 112, and an operating system 114.Internet protocol notifications may be stored in the memory 112 whenreceived at the mobile communication device 102. The device 102 isconfigured to use the radio transceiver 110 to establish a wirelesscommunication link with a base transceiver station (BTS) 124, and thebase transceiver station 124 provides communications connectivity of thedevice 102 to a network 122. One or more servers 120 that are coupled toone or more provider servers 118 may also have access to the network122. The provider server 118 may be a third party publisher and maypublish the internet protocol notifications 126 to the server 120. Forexample, the provider server 118 may be a server from a company thatdesires to promote its products with push internet protocolnotifications. The server 120 may then push the internet protocolnotifications 126 that are received from the provider server 118 to themobile device 102. The network 122 may comprise any combination ofprivate and public networks.

It is understood that the system 100 may comprise any number of mobilecommunication devices 102 and any number of base transceiver stations124. The collectivity of base transceiver stations 124 may be said tocomprise a radio access network, in that these base transceiver stations124 may provide a radio communication link to the mobile communicationdevices 102 to provide access to the network 122. The radio accessnetwork may be abstracted in different ways and may comprise, inaddition to the base transceiver stations 124, servers and data storessuch as home location registers (HLRs) or servers that implement thefunctionality of home location registers, visitor location registers(VLRs) or servers that implement the functionality of visitor locationregisters, base station controllers (BSCs), mobile switching centers(MSCs), and other network nodes that are specifically associated withproviding wireless access and connectivity to the mobile communicationdevices 102.

The radio transceiver 110 may communicate with the base transceiverstation 124 using any of a variety of wireless communication protocolsincluding a code division multiple access (CDMA) wireless communicationprotocol, a global system for mobile communication (GSM) wirelesscommunication protocol, a long-term evolution (LTE) wirelesscommunication protocol, a world-wide interoperability for microwaveaccess (WiMAX) wireless communication protocol, or another wirelesscommunication protocol. The device 102 may be any of a mobile phone, apersonal digital assistant (PDA), a media player, a wireless enabledcomputer, or other mobile communication device. In an embodiment, themobile communication device 102 may have other components (not shown)such as a near field communication (NFC) radio transceiver, a wirelesslocal area network (WLAN) radio transceiver, or other components.

The location of the mobile communication device 102 may be determined ina variety of ways. For example, the locating process may be accomplishedin a network-based manner, in a handset-based manner, in a hybrid mannerthat involves both the network-based technologies and handset-basedtechnologies, or in another manner for mobile communicationlocalization.

In a network-based localization system, nearby base transceiver stations124 may take some signal parameter measurements and relay themeasurements to a data fusion center where the measurements areprocessed and the location of the mobile communication device 102 isdetermined. In a handset-based localization system, some client softwaremay be installed on the mobile communication device 102 to determine thelocation of the mobile communication device 102. In an embodiment, themobile communication device 102 may compute its location by cellidentification, signal strength of the home and neighboring cells andsend the location information back to the server 120. If the mobilecommunication device 102 is also equipped with a GPS receiver 108, thenmore precise location information may be sent from the mobilecommunication device 102 to the server 120. In a hybrid mechanism, acombination of network-based and handset-based technologies are used forlocation determination of the mobile communication device 102.

The server 120 may compare the location of the mobile communicationdevice 102 with geo-fences on a map. The map may be a mathematicabstraction of an area. For example, the map may comprise triangles,quadrangles, hexagons, or another regular or irregular shape with theiredges as geo-fences. The map may be defined by the coordinates of thevertices of the figures or polygons. The map may be a combination ofdifferent regular and/or irregular shapes with their edges asgeo-fences. The map may cover a certain area around certain points ofinterest, for example the map may cover the areas within a radius of 1mile, 3 miles, 10 miles, or another radius around the nearest three basetransceiver stations 124 from the mobile communication device 102. Themap may gradually or discretely change to another map when the mobilecommunication device 102 travels. A geo-fence may be a user-definedvirtual perimeter for a geographic area. For example, a geo-fence on themap that the server 120 utilizes here may be a virtual perimeter of aparticular store territory or a brand territory on the map. The range ofthe geo-fence around a brand or store may vary based on the brand orstore. For example, the geo-fence of a high-end grocery store may be acircle with a radius of 3 miles around the high-end grocery store. Asanother example, a geo-fence for a coffee shop may be a circle with aradius of half a mile around the coffee shop. The range of the geo-fencemay also vary when the user of the mobile communication device 102 istraveling in different ways. For example, the geo-fence may be a circlewith a radius of half a mile around the coffee shop when the user of themobile communication device 102 is driving. The geo-fence may be acircle with a radius of 50 feet around the coffee shop when the user ofthe mobile communication device 102 is walking. When the mobilecommunication device 102 is detected by the server 120 to have entered ageo-fenced area, the server 120 may send an internet protocolnotification 126 to the mobile communication device 102. The internetprotocol notification 126 may be a coupon, a voucher, an offer, or areward program status from a brand or store.

The total number of the internet protocol notifications 126 sent to asingle user may be limited to a predefined amount within a predefinedperiod of time. For example, the total number of the internet protocolnotifications 126 may be limited to two per day, five per day, ten perday, or another number for each day. The total number of internetprotocol notification 126 may be limited to 20, 50, or 100 a month, oranother amount for each month. The user may opt out of the subscriptionof the internet protocol notification 126 by any brand or store from theserver 120 at any time. The user may choose to subscribe to only some ofthe internet protocol notifications 126 the server 120 publishes.

When the internet protocol notification 126 is received at the mobilecommunication device 102, the internet protocol notification 126 isplaced in the memory 112 for immediate action. For example, the internetprotocol notification 126 may be forwarded to a display application atthe mobile communication to display at the minimum possible delay. Thecorresponding client application 106 to the internet protocolnotification 126 may also be notified by the mobile communication device102 and take further action at the minimum delay.

Turning now to FIG. 2, a communication system 200 is described. In anembodiment, an internet protocol notification 126 may be published by aprovider server 118. A server computer 120 may retrieve the internetprotocol notification 126 from the provider server 118. The server 120may then send the internet protocol notification 126 to a mobilecommunication device 102 if the mobile communication device 102subscribes to the internet protocol notifications 126 from the providerserver 118. At the mobile communication device 102, the internetprotocol notification 126 may be displayed by a screen of the mobilecommunication device 102. Additionally, the internet protocolnotification 126 may be forwarded to a client application 106 that iscorresponding to the provider server 118 and the internet protocolnotification 126 for further action.

Turning now to FIG. 3, a method 300 is described. At block 302, the sizeof physically addressable random access memory (RAM) and the number ofcentral processing unit (CPU) cores of the server computer aredetermined at boot time. In an embodiment, the process of determiningthe size of the physically addressable random access memory and thenumber of the central processing unit cores at boot time may beaccomplished in an automated manner. For example, an application on theserver computer, for example the application 128 in FIG. 1, may examinethe size of the physically addressable random access memory and thenumber of the central processing unit cores at boot time for furtheraction. In an embodiment, the size of the physically addressable randomaccess memory in the entire system of the server, for example the server120 in FIG. 1, is examined before the conventionally configured limitfor the file handles is changed so that the random access memory may beutilized instead of the disk memory for the internet protocolnotification architecture. The speed of accessing the random accessmemory is much faster than the disk memory and so by utilizing therandom access memory instead of the disk memory, better performance ofthe internet protocol notification service may be achieved.

The size of the physically addressable random access memory and thenumber of central processing unit cores may be utilized with theoperational or system overhead to determine the value of some kernelparameters. The operational or system overhead may be the hardwareand/or software cost for the operating system without other applicationsrunning on the server. For example, the upper bound of the number ofopen file descriptors or file handles of the entire system, the upperbound of the number of open file descriptors or file handles perprocess, or the upper bound of the number of open file descriptors orfile handles per thread is limited based on the available physicallyaddressable random access memory.

In an embodiment, two file handles may be utilized to keep acommunication session, for example, a transmission control protocolsession, alive at all times. When a large number of concurrent opentransmission control protocol connections are in need, it benefits thetrue push internet protocol notification system to set the limit for thetotal number of file handles in the entire system to the maximum numberconsistent with the hardware and/or software limits.

At block 304, the resource limit, rlimit, in the kernel of the servercomputer is set that comprises setting the limit for the total number offile handles in the entire system automatically based on the determinedsize of random access memory and the determined number of the centralprocessing unit cores at boot time. For example, the application 128 inFIG. 1 may automatically set the resource limit in the kernel based onthe determined size of random access memory, the determined number ofcentral processing unit cores, and the operational or system overhead.For example, the limit for the number of file handles is determinedbased on the size of the random access memory, the number of centralprocessing unit cores, and the system overhead. To push internetprotocol notifications in real time, network connections between theserver and the client may desire to be kept open for all times as longas the server is up. If a network connection is initiated when it isneeded instead of being kept open for all times, much time may be wastedestablishing the connection.

In an embodiment, if there are a large number of devices subscribing toreal-time push notifications, a large number of concurrent openconnections may be involved. To provide a large number of concurrentconnections using servers with conventionally configured kernelsinvolves having too many server computers and hence an inefficient useof capital equipment. The conventionally configured kernel parametersmay be removed and new kernel parameters may be determined based on thesize of the physically addressable random access memory, the number ofcentral processing unit cores, and the operational or system overhead.Average servers come with conventionally configured kernel parametersthat are set for different uses. For example, these conventionallyconfigured kernels may be designed for multi-process environment.Conventionally configured kernels may not be appropriate or optimal forsingle-process environment, for example for true push architecture forinternet protocol notifications. Hence, it may make sense to change thekernel parameters to meet the specific needs of the server with truepush architecture.

The limit for the total number of file handles may limit the totalnumber of open files in the entire system. The limit of the number ofopen input files is set to the maximum number consistent with the randomaccess memory size. The limit of the number of open output files is setto the maximum number consistent with the random access memory size. Thelimit for the number of concurrent network connections is set based onthe number of the central processing unit cores and the size of therandom access memory determined at boot time. In addition, the limit forthe number of concurrent transmission control protocol connections isset based on the size of the random access memory determined at boottime. In an embodiment, the limit for the total number of open files bya single process may be set. Other kernel parameters may also be changedbased on the determined size of the random access memory, the determinednumber of the central processing unit cores, and the system overhead atboot time.

At block 306, the memory page allocation is tied into the setting of thekernel parameters. In an embodiment, this step is also conducted by theapplication 128 automatically. Some shared memory related limits of theserver may be set to achieve better input/output performance. Forexample, the maximum size of a shared memory segment, the minimum sizeof a shared memory segment, the total amount of shared memory available,the maximum number of shared memory segments per process, the maximumnumber of shared memory segments in the entire system, semaphores thatallow different processes to synchronize their access to certainresources, or another shared memory related limit may be set.

At block 308, the central processing unit core affinity is set to asingle thread for the server computer to avoid context switching betweenapplications. For example, the application 128 may set the centralprocessing unit core affinity to a single thread or a single process.Each central processing unit core may be coupled to a single thread.Multi-threads may not be coupled to the same central processing unitcore. With the central processing unit core affinity set to a singlethread, context switching between applications may be avoided. Contextswitching may significantly slow down the application processing by thecentral processing units. Hence, avoiding context switching mayaccelerate the processing of applications.

At block 310, the input/output (I/O) maintenance of the server computeris maximized for concurrent web sockets so that the server computer isoptimized for implementing the true push for internet protocolnotification. With blocks 302 through 308, the input/output maintenanceof the server may be maximized. For the true push for internet protocolnotifications, the server may maintain a large number of live networkconnections with the mobile communication devices to which the serverwants to push internet protocol notifications. The true pusharchitecture may also introduce a large number of input/outputoperations with the live network connections. A web socket or networksocket is network interface, an endpoint of an inter-processcommunication flow across a computer network. The address of a websocket is the combination of an internet protocol address and a portnumber. For example, the input/output maintenance may be maximized whenpredominantly dormant web sockets are present. Predominantly dormant websockets are web sockets that are connected but with no traffic goingthrough. Web connections may be kept alive so that internet protocolnotifications may be pushed to the mobile communication devices at theminimum possible delay when it is entailed. However, no traffic may gothrough most of the connected network connections most of the time.Thus, maximizing the input/output maintenance may benefit the serverwhen predominantly dormant web sockets are present.

FIG. 4 depicts the mobile device 400, which is operable for implementingaspects of the present disclosure, but the present disclosure should notbe limited to these implementations. Though illustrated as a mobilephone, the mobile device 400 may take various forms including a wirelesshandset, a pager, a personal digital assistant (PDA), a gaming device,or a media player. The mobile device 400 includes a display 402 and atouch-sensitive surface and/or keys 404 for input by a user. The mobiledevice 400 may present options for the user to select, controls for theuser to actuate, and/or cursors or other indicators for the user todirect. The mobile device 400 may further accept data entry from theuser, including numbers to dial or various parameter values forconfiguring the operation of the handset. The mobile device 400 mayfurther execute one or more software or firmware applications inresponse to user commands. These applications may configure the mobiledevice 400 to perform various customized functions in response to userinteraction. Additionally, the mobile device 400 may be programmedand/or configured over-the-air, for example from a wireless basestation, a wireless access point, or a peer mobile device 400. Themobile device 400 may execute a web browser application which enablesthe display 402 to show a web page. The web page may be obtained viawireless communications with a base transceiver station, a wirelessnetwork access node, a peer mobile device 400 or any other wirelesscommunication network or system.

FIG. 5 shows a block diagram of the mobile device 400. While a varietyof known components of handsets are depicted, in an embodiment a subsetof the listed components and/or additional components not listed may beincluded in the mobile device 400. The mobile device 400 includes adigital signal processor (DSP) 502 and a memory 504. As shown, themobile device 400 may further include an antenna and front end unit 506,a radio frequency (RF) transceiver 508, a baseband processing unit 510,a microphone 512, an earpiece speaker 514, a headset port 516, aninput/output interface 518, a removable memory card 520, a universalserial bus (USB) port 522, an infrared port 524, a vibrator 526, akeypad 528, a touch screen liquid crystal display (LCD) with a touchsensitive surface 530, a touch screen/LCD controller 532, a camera 534,a camera controller 536, and a global positioning system (GPS) receiver538. In an embodiment, the mobile device 400 may include another kind ofdisplay that does not provide a touch sensitive screen. In anembodiment, the DSP 502 may communicate directly with the memory 504without passing through the input/output interface 518. Additionally, inan embodiment, the mobile device 400 may comprise other peripheraldevices that provide other functionality.

The DSP 502 or some other form of controller or central processing unitoperates to control the various components of the mobile device 400 inaccordance with embedded software or firmware stored in memory 504 orstored in memory contained within the DSP 502 itself. In addition to theembedded software or firmware, the DSP 502 may execute otherapplications stored in the memory 504 or made available via informationcarrier media such as portable data storage media like the removablememory card 520 or via wired or wireless network communications. Theapplication software may comprise a compiled set of machine-readableinstructions that configure the DSP 502 to provide the desiredfunctionality, or the application software may be high-level softwareinstructions to be processed by an interpreter or compiler to indirectlyconfigure the DSP 502.

The DSP 502 may communicate with a wireless network via the analogbaseband processing unit 510. In some embodiments, the communication mayprovide Internet connectivity, enabling a user to gain access to contenton the Internet and to send and receive e-mail or text messages. Theinput/output interface 518 interconnects the DSP 502 and variousmemories and interfaces. The memory 504 and the removable memory card520 may provide software and data to configure the operation of the DSP502. Among the interfaces may be the USB port 522 and the infrared port524. The USB port 522 may enable the mobile device 400 to function as aperipheral device to exchange information with a personal computer orother computer system. The infrared port 524 and other optional portssuch as a Bluetooth® interface or an IEEE 802.11 compliant wirelessinterface may enable the mobile device 400 to communicate wirelesslywith other nearby handsets and/or wireless base stations.

The keypad 528 couples to the DSP 502 via the interface 518 to provideone mechanism for the user to make selections, enter information, andotherwise provide input to the mobile device 400. Another inputmechanism may be the touch screen LCD 530, which may also display textand/or graphics to the user. The touch screen LCD controller 532 couplesthe DSP 502 to the touch screen LCD 530. The GPS receiver 538 is coupledto the DSP 502 to decode global positioning system signals, therebyenabling the mobile device 400 to determine its position.

FIG. 6A illustrates a software environment 602 that may be implementedby the DSP 502. The DSP 502 executes operating system software 604 thatprovides a platform from which the rest of the software operates. Theoperating system software 604 may provide a variety of drivers for thehandset hardware with standardized interfaces that are accessible toapplication software. The operating system software 604 may be coupledto and interact with application management services (AMS) 606 thattransfer control between applications running on the mobile device 400.Also shown in FIG. 6A are a web browser application 608, a media playerapplication 610, and JAVA applets 612. The web browser application 608may be executed by the mobile device 400 to browse content and/or theInternet, for example when the mobile device 400 is coupled to a networkvia a wireless link. The web browser application 608 may permit a userto enter information into forms and select links to retrieve and viewweb pages. The media player application 610 may be executed by themobile device 400 to play audio or audiovisual media. The JAVA applets612 may be executed by the mobile device 400 to provide a variety offunctionality including games, utilities, and other functionality.

FIG. 6B illustrates an alternative software environment 620 that may beimplemented by the DSP 502. The DSP 502 executes operating systemsoftware 628 (for example an operating system kernel) and an executionruntime 630. The DSP 502 executes applications 622 that may execute inthe execution runtime 630 and may rely upon services provided by theapplication framework 624. Applications 622 and the applicationframework 624 may rely upon functionality provided via the libraries626.

FIG. 7 illustrates a computer system 380 suitable for implementing oneor more embodiments disclosed herein. The computer system 380 includes aprocessor 382 (which may be referred to as a central processor unit orCPU) that is in communication with memory devices including secondarystorage 384, read only memory (ROM) 386, random access memory (RAM) 388,input/output (I/O) devices 390, and network connectivity devices 392.The processor 382 may be implemented as one or more CPU chips.

It is understood that by programming and/or loading executableinstructions onto the computer system 380, at least one of the CPU 382,the RAM 388, and the ROM 386 are changed, transforming the computersystem 380 in part into a particular machine or apparatus having thenovel functionality taught by the present disclosure. It is fundamentalto the electrical engineering and software engineering arts thatfunctionality that can be implemented by loading executable softwareinto a computer can be converted to a hardware implementation by wellknown design rules. Decisions between implementing a concept in softwareversus hardware typically hinge on considerations of stability of thedesign and numbers of units to be produced rather than any issuesinvolved in translating from the software domain to the hardware domain.Generally, a design that is still subject to frequent change may bepreferred to be implemented in software, because re-spinning a hardwareimplementation is more expensive than re-spinning a software design.Generally, a design that is stable that will be produced in large volumemay be preferred to be implemented in hardware, for example in anapplication specific integrated circuit (ASIC), because for largeproduction runs the hardware implementation may be less expensive thanthe software implementation. Often a design may be developed and testedin a software form and later transformed, by well known design rules, toan equivalent hardware implementation in an application specificintegrated circuit that hardwires the instructions of the software. Inthe same manner as a machine controlled by a new ASIC is a particularmachine or apparatus, likewise a computer that has been programmedand/or loaded with executable instructions may be viewed as a particularmachine or apparatus.

The secondary storage 384 is typically comprised of one or more diskdrives or tape drives and is used for non-volatile storage of data andas an over-flow data storage device if RAM 388 is not large enough tohold all working data. Secondary storage 384 may be used to storeprograms which are loaded into RAM 388 when such programs are selectedfor execution. The ROM 386 is used to store instructions and perhapsdata which are read during program execution. ROM 386 is a non-volatilememory device which typically has a small memory capacity relative tothe larger memory capacity of secondary storage 384. The RAM 388 is usedto store volatile data and perhaps to store instructions. Access to bothROM 386 and RAM 388 is typically faster than to secondary storage 384.The secondary storage 384, the RAM 388, and/or the ROM 386 may bereferred to in some contexts as computer readable storage media and/ornon-transitory computer readable media.

I/O devices 390 may include printers, video monitors, liquid crystaldisplays (LCDs), touch screen displays, keyboards, keypads, switches,dials, mice, track balls, voice recognizers, card readers, paper tapereaders, or other well-known input devices.

The network connectivity devices 392 may take the form of modems, modembanks, Ethernet cards, universal serial bus (USB) interface cards,serial interfaces, token ring cards, fiber distributed data interface(FDDI) cards, wireless local area network (WLAN) cards, radiotransceiver cards such as code division multiple access (CDMA), globalsystem for mobile communications (GSM), long-term evolution (LTE),worldwide interoperability for microwave access (WiMAX), and/or otherair interface protocol radio transceiver cards, and other well-knownnetwork devices. These network connectivity devices 392 may enable theprocessor 382 to communicate with the Internet or one or more intranets.With such a network connection, it is contemplated that the processor382 might receive information from the network, or might outputinformation to the network in the course of performing theabove-described method steps. Such information, which is oftenrepresented as a sequence of instructions to be executed using processor382, may be received from and outputted to the network, for example, inthe form of a computer data signal embodied in a carrier wave.

Such information, which may include data or instructions to be executedusing processor 382 for example, may be received from and outputted tothe network, for example, in the form of a computer data baseband signalor signal embodied in a carrier wave. The baseband signal or signalembedded in the carrier wave, or other types of signals currently usedor hereafter developed, may be generated according to several methodswell known to one skilled in the art. The baseband signal and/or signalembedded in the carrier wave may be referred to in some contexts as atransitory signal.

The processor 382 executes instructions, codes, computer programs,scripts which it accesses from hard disk, floppy disk, optical disk(these various disk based systems may all be considered secondarystorage 384), ROM 386, RAM 388, or the network connectivity devices 392.While only one processor 382 is shown, multiple processors may bepresent. Thus, while instructions may be discussed as executed by aprocessor, the instructions may be executed simultaneously, serially, orotherwise executed by one or multiple processors. Instructions, codes,computer programs, scripts, and/or data that may be accessed from thesecondary storage 384, for example, hard drives, floppy disks, opticaldisks, and/or other device, the ROM 386, and/or the RAM 388 may bereferred to in some contexts as non-transitory instructions and/ornon-transitory information.

In an embodiment, the computer system 380 may comprise two or morecomputers in communication with each other that collaborate to perform atask. For example, but not by way of limitation, an application may bepartitioned in such a way as to permit concurrent and/or parallelprocessing of the instructions of the application. Alternatively, thedata processed by the application may be partitioned in such a way as topermit concurrent and/or parallel processing of different portions of adata set by the two or more computers. In an embodiment, virtualizationsoftware may be employed by the computer system 380 to provide thefunctionality of a number of servers that is not directly bound to thenumber of computers in the computer system 380. For example,virtualization software may provide twenty virtual servers on fourphysical computers. In an embodiment, the functionality disclosed abovemay be provided by executing the application and/or applications in acloud computing environment. Cloud computing may comprise providingcomputing services via a network connection using dynamically scalablecomputing resources. Cloud computing may be supported, at least in part,by virtualization software. A cloud computing environment may beestablished by an enterprise and/or may be hired on an as-needed basisfrom a third party provider. Some cloud computing environments maycomprise cloud computing resources owned and operated by the enterpriseas well as cloud computing resources hired and/or leased from a thirdparty provider.

In an embodiment, some or all of the functionality disclosed above maybe provided as a computer program product. The computer program productmay comprise one or more computer readable storage medium havingcomputer usable program code embodied therein to implement thefunctionality disclosed above. The computer program product may comprisedata structures, executable instructions, and other computer usableprogram code. The computer program product may be embodied in removablecomputer storage media and/or non-removable computer storage media. Theremovable computer readable storage medium may comprise, withoutlimitation, a paper tape, a magnetic tape, magnetic disk, an opticaldisk, a solid state memory chip, for example analog magnetic tape,compact disk read only memory (CD-ROM) disks, floppy disks, jump drives,digital cards, multimedia cards, and others. The computer programproduct may be suitable for loading, by the computer system 380, atleast portions of the contents of the computer program product to thesecondary storage 384, to the ROM 386, to the RAM 388, and/or to othernon-volatile memory and volatile memory of the computer system 380. Theprocessor 382 may process the executable instructions and/or datastructures in part by directly accessing the computer program product,for example by reading from a CD-ROM disk inserted into a disk driveperipheral of the computer system 380. Alternatively, the processor 382may process the executable instructions and/or data structures byremotely accessing the computer program product, for example bydownloading the executable instructions and/or data structures from aremote server through the network connectivity devices 392. The computerprogram product may comprise instructions that promote the loadingand/or copying of data, data structures, files, and/or executableinstructions to the secondary storage 384, to the ROM 386, to the RAM388, and/or to other non-volatile memory and volatile memory of thecomputer system 380.

In some contexts, the secondary storage 384, the ROM 386, and the RAM388 may be referred to as a non-transitory computer readable medium or acomputer readable storage media. A dynamic RAM embodiment of the RAM388, likewise, may be referred to as a non-transitory computer readablemedium in that while the dynamic RAM receives electrical power and isoperated in accordance with its design, for example during a period oftime during which the computer system 380 is turned on and operational,the dynamic RAM stores information that is written to it. Similarly, theprocessor 382 may comprise an internal RAM, an internal ROM, a cachememory, and/or other internal non-transitory storage blocks, sections,or components that may be referred to in some contexts as non-transitorycomputer readable media or computer readable storage media.

While several embodiments have been provided in the present disclosure,it should be understood that the disclosed systems and methods may beembodied in many other specific forms without departing from the spiritor scope of the present disclosure. The present examples are to beconsidered as illustrative and not restrictive, and the intention is notto be limited to the details given herein. For example, the variouselements or components may be combined or integrated in another systemor certain features may be omitted or not implemented.

Also, techniques, systems, subsystems, and methods described andillustrated in the various embodiments as discrete or separate may becombined or integrated with other systems, modules, techniques, ormethods without departing from the scope of the present disclosure.Other items shown or discussed as directly coupled or communicating witheach other may be indirectly coupled or communicating through someinterface, device, or intermediate component, whether electrically,mechanically, or otherwise. Other examples of changes, substitutions,and alterations are ascertainable by one skilled in the art and could bemade without departing from the spirit and scope disclosed herein.

What is claimed is:
 1. A method of true push for internet protocolnotification implemented by at least one server computer, comprising:determining, by an application stored in a non-transitory memory of aserver computer and executed by a processor of the server computer, asize of physically addressable random access memory and a number ofcentral processing unit cores of the server computer at boot time;changing, by the application, parameters on a kernel of the servercomputer based on the size of the physically addressable random accessmemory and the number of central processing unit cores at boot time; andsetting, by the application, central processing unit core affinity to asingle thread for the server computer to avoid context switching betweenapplications, whereby input/output maintenance of the server computer ismaximized so that the server computer is optimized for implementing thetrue push for internet protocol notification.
 2. The method of claim 1,wherein a conventionally configured limit of a total number of filehandles is removed for an entire system of the server computer.
 3. Themethod of claim 2, wherein a limit for a number of file handles in theentire system is determined based on the number of central processingunit cores, the size of the random access memory, and the entire systemoverhead.
 4. The method of claim 1, wherein a limit for a number of openinput files is set to a maximum number consistent with the random accessmemory size.
 5. The method of claim 1, wherein a limit for a number ofopen output files is set to the maximum number consistent with therandom access memory size.
 6. The method of claim 1, wherein a limit fora number of concurrent network connections is set based on the randomaccess memory size determined at boot time.
 7. A method of true push forinternet protocol notification to a mobile communication deviceimplemented by at least one server computer, comprising: setting, by anapplication stored in a non-transitory memory of a server computer andexecuted by a processor of the server computer, central processing unitcore affinity to a single thread for the server computer to avoidcontext switching between applications, whereby input/output maintenanceof the server computer is maximized for concurrent web sockets so thatthe server computer is optimized for implementing the true push forinternet protocol notification.
 8. The method of claim 7, furthercomprising determining, by the application, a size of physicallyaddressable random access memory and a number of central processing unitcores of the server computer at boot time.
 9. The method of claim 8,further comprising setting, by the application, a limit for a number ofconcurrent transmission control protocol connections based on the sizeof the random access memory determined at boot time.
 10. The method ofclaim 8, wherein a conventionally configured limit for a total number offile handles on an entire system of the server computer is removed andan algorithmically defined limit is set automatically based on thedetermined size of the physically addressable random access memory andthe determined number of central processing unit cores of the server atboot time.
 11. The method of claim 10, wherein the size of thephysically addressable random access memory in the entire system of theserver is examined before the conventionally configured limit for thefile handles is changed to ensure the random access memory instead of adisk memory is used in the internet protocol notification architectureto achieve faster server performance.
 12. The method of claim 8, furthercomprising setting, by the application, a limit for a total number ofopen files by a single process.
 13. The method of claim 8, furthercomprising setting, by the application, at least one of: a limit for amaximum size of a shared memory segment, a limit for a minimum size of ashared memory segment, or a limit for a total amount of shared memoryavailable in the server computer.
 14. The method of claim 8, furthercomprising setting, by the application, at least one of: a limit for amaximum number of shared memory segments per process, a limit for amaximum number of shared memory segments in an entire system of theserver computer, or a limit for semaphores in the entire system of theserver computer.
 15. A method of true push for internet protocolnotification to a mobile communication device implemented by at leastone server computer, comprising: tying, by an application stored in anon-transitory memory of a server computer and executed by a processorof the server computer, a memory page allocation into a setting ofkernel parameters, whereby input/output maintenance of the servercomputer is maximized for concurrent web sockets so that the servercomputer is optimized for implementing the true push for internetprotocol notification.
 16. The method of claim 15, further comprising:determining, by the application, a size of physically addressable randomaccess memory and a number of central processing unit cores of theserver computer at boot time; and changing, by the application,parameters on a kernel of the server computer based on the size of thephysically addressable random access memory and the number of centralprocessing unit cores at boot time.
 17. The method of claim 16, whereina limit for a number of open input files is set to a maximum numberconsistent with the random access memory size.
 18. The method of claim16, wherein a limit for a number of open output files is set to themaximum number consistent with the random access memory size.
 19. Themethod of claim 16, wherein a limit for a number of concurrent networkconnections is set based on the random access memory size determined atboot time.
 20. The method of claim 16, wherein a limit for a number offile handles in an entire system is determined based on the number ofcentral processing unit cores, the size of the random access memory, andthe entire system overhead.